how should names look like?

- In my opinion if we want to stay clear we should use prefix "__" for all
  internal stuff and prohibit user from using any name starting with "__".

- Macros used directly by user can have names without prefix, nobody wants
  "__PROC".  All which aren't must start with "__"

- To names themself, we can have
    INCLUDEALLGLOBALS
    includeallglobals
    IncludeAllGlobals
    Include_All_Globals
    include_all_globals
  and let us not forget about exception, like "PROC" everyone is used to have
  it uppercase, and "struc"+"ends", everyone wants it lowercase, while things
  like "IncludeAllGlobals" looks best capitalized. I think uppercase names
  should stay left for structures (is it acceptable to establish "proc"? ).
  Lowercase is unsuitable for multi-word names, so we can use
    include_all_globals
    IncludeAllGlobals
    includeAllGlobals
  second looks better, but then "struc" would have to be "Struc" etc. Generally
  macrosyntax is emulating syntax, so we should really use lowercase. It also 
  helps to differentiate from capitalized names of procedures. But on other
  side for names like IncludeAllGlobals it is ugly.  ?????

  I think solution could be capitalizing from second word, like variable names
  in Java - "includeAllGlobals", but it's rather new.
  
- Another problem are names coming from TASM standard starting with dot like
  ".code", ".if", i think dot here is absolutely against FASM's meaning of dot.
  We should stop this until it's possible. Now is the valuable time when we can
  break backward compatibility, who knows when next cleanup will be possible?
  Remember problems someone had with structure member ".data" after declaring
  TASM-like macro ".data"?

- I think procedures should have name of routinepack plus dot as prefix. We
  could use "_" instead of ".", but i think this is what "." in name should
  mean and is right at it's place here.

- Names of routinepacks and procedures should be capitalized, so we will have 
  names like "Mem.Alloc", "OpenGL.InitSomething" etc.

- if routinepacks declares variables which can be accessed by user, they should
  have separate name format. It can be either capitalized-from-second-word like
  macros (ambiguity isn't too big here), or lowercase with underscores ("_").
